-
Notifications
You must be signed in to change notification settings - Fork 387
💡New command - Import-PnPFlow #4854
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
💡New command - Import-PnPFlow #4854
Conversation
Thank you! Can you please also add documentation for this cmdlet? Please create a corresponding .md file in the documents folder for that. |
Hello @erwinvanhunen I am still testing this, and need to make more refining, Would be finishing it soon. Thanks, |
Hello @erwinvanhunen & @gautamdsheth Now the testing is done and ready for review. Thanks, |
Hey @gautamdsheth Final refactoring has been completed and the documentation updated. This is now ready for review. Thanks, |
Type
Related Issues?
Fixes #4816, partially fixes #Y, mentioned in #Z, etc.
What is in this Pull Request ?
New command to import a flow from a .zip package.
Import-PnPFlow
SYNTAX
DESCRIPTION
This cmdlet Imports a Microsoft Power Automate Flow from a zip package.
Many times Importing a Microsoft Power Automate Flow will not be possible due to various reasons such as connections having gone stale, SharePoint sites referenced no longer existing or other configuration errors in the Flow. To display these errors when trying to Import a Flow, provide the -Verbose flag with your Import request. If not provided, these errors will silently be ignored.
EXAMPLES
Example 1
This will Import the specified Microsoft Power Automate Flow from the specified Power Platform environment as an output to the current output of PowerShell
Example 2
This will Import the specified Microsoft Power Automate Flow from the default Power Platform environment as an output to the current output of PowerShell
Example 3
This will Import a flow to the default environment. The flow will be imported as a zip package. The name of the flow will be set to NewFlowName.
Example 4
This will Import a flow to the default environment. The flow will be imported as a zip package. The name of the flow will be set to NewFlowName. With the -Verbose flag, any errors that occur during the import process will be displayed in the console.
Test Screens
Screen 1
Screen 2
PARAMETERS
-Connection
Optional connection to be used by the cmdlet.
Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection.
-Environment
The name of the Power Platform environment or an Environment instance. If omitted, the default environment will be used.
-PackagePath
Local path of the .zip package to import. The path must be a valid path on the local file system.
-Name
The new name of the flow.
Thanks,
Nish